Sourced from github.com/opencontainers/runc's releases.

runc v1.3.5 -- "Lo viejo funciona!"

This is the fifth patch release of the 1.3.z release series of runc, and primarily contains a few fixes for issues found in 1.3.4.

Fixed

• Recursive atime-related mount flags (rrelatime et al.) are now applied properly. (#5115, #5098)
• PR #4757 caused a regression that resulted in spurious cannot start a container that has stopped errors when running runc create and has thus been reverted. (#5158, #5153, #5151, #4645, #4757)

Changed

• Updated builds to Go 1.25, libseccomp v2.6.0. (#5111, #5053)
• Minor signing keyring updates. (#5146, #5139, #5144, #5148)

Static Linking Notices

The runc binary distributed with this release are statically linked with the following GNU LGPL-2.1 licensed libraries, with runc acting as a "work that uses the Library":

• libseccomp

The versions of these libraries were not modified from their upstream versions, but in order to comply with the LGPL-2.1 (§6(a)), we have attached the complete source code for those libraries which (when combined with the attached runc source code) may be used to exercise your rights under the LGPL-2.1.

However we strongly suggest that you make use of your distribution's packages or download them from the authoritative upstream sources, especially since these libraries are related to the security of your containers.

---

Thanks to the following contributors for making this release possible:

• Aleksa Sarai cyphar@cyphar.com
• Kir Kolyshkin kolyshkin@gmail.com
• Li Fu Bang lifubang@acmcoder.com
• Ricardo Branco rbranco@suse.de

Sourced from github.com/opencontainers/runc's changelog.

[1.3.6] - 2026-06-13

On no account should you allow a Vogon to read poetry at you.

Security

This release includes a fix for the following low-severity security issue:

• CVE-2026-41579 allowed a malicious image with a /dev symlink to have limited write access to the host filesystem in ways that our analysis indicates was too limited to be problematic in practice. This bug was very similar to those fixed in [CVE-2025-31133][], [CVE-2025-52565][], [CVE-2025-31133][] and was simply missed at the time when we hardened the rootfs preparation code. We have conducted a deeper audit and not found any other problematic cases.

  This patchset required backports for #5190 and #5285, which were primarily code reorganisations that were already backported to runc 1.4 and 1.5.

Fixed

• A regression in runc v1.3.0 which can result in a stuck runc exec or runc run when the container process runs for a short time. (#5208, #5210, #5215)
• Various integration test improvements. (#5159, #5188, #5226, #5228, #5239, #5253, #5269, #5288)

Changed

• When masking directories with maskPaths, runc will now reuse a single tmpfs instance (which is not writable) to reduce the number tmpfs superblocks that need to be reaped when containers die (in particular, Kubernetes applies masks to per-CPU sysfs directories which get expensive quickly). (#5275, #5281)

[1.5.0-rc.2] - 2026-04-02

いざやいざや、見に行かん

[!NOTE] runc v1.5.0-rc.2 includes all of the patches backported to runc v1.4.2.

Fixed

• Building with libpathrs for systems that use non-GNU awk, e.g. Debian. (#5196, #5194)

Added

• Installation notes for libpathrs. (#5199, #5195)
• Support for specs.LinuxSeccompFlagWaitKillableRecv. (#5183, #5172)
• When building runc, RUNC_BUILDTAGS make or shell environment variable can

... (truncated)

• 491b69b VERSION: release v1.3.6
• d934454 merge CVE-2026-41579 fixes into release-1.3
• 9432ad3 rootfs: make cgroupv1 subsystem symlinks fd-based
• a8e53f2 rootfs: make /dev initialisation code fd-based
• 78c50d4 rootfs: switch createDevices argument order
• 083e21e libct: use preopened rootfs more
• 42cfcbe Pre-open container root directory
• 2e9b6a8 libct: minor refactor in mountToRootfs
• edf5328 libct: mountCgroupV1: address TODO
• 3661a9d integration: add some tests for bind mount through dangling symlinks
• Additional commits viewable in compare view